Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1118

reference: 515-tree-1
name: 1118
tree-preservation-order: undefined
515-tpo-1
uprn
address-text
point: POINT (-1.021477 50.898668)
geometry: MULTIPOLYGON (((-1.021420 50.898662,-1.021423 50.898673,-1.021430 50.898684,-1.021443 50.898692,-1.021459 50.898697,-1.021476 50.898699,-1.021494 50.898697,-1.021510 50.898692,-1.021522 50.898684,-1.021531 50.898674,-1.021534 50.898663,-1.021531 50.898652,-1.021523 50.898642,-1.021511 50.898634,-1.021495 50.898629,-1.021478 50.898627,-1.021460 50.898628,-1.021444 50.898633,-1.021431 50.898641,-1.021423 50.898651,-1.021420 50.898662)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL